CI pipeline repair #1104
Merged
CI pipeline repair #1104
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I updated the workflows to github actions v4 and haskell actions v2. Also
created: dedicated stack and windows CI files to display in the README and for
better separation of concerns. Plus, I downgraded to hosc-0.20 because the
working CI pipelines reveal that there are breaking changes made in hosc-0.21 as
discussed in issue #1103.
The new GHC entries support the recommended ghcup GHC/cabal combinations.
The linux CI also uses the recommended ghcup settings + the debian GHC (9.0.2) and cabal (3.4.1.0) versions as reference.
I did not touch the build listener CI/release pipeline; they are still broken but probably less priority than
the overall build CI and needs to be investigated in a new PR.
Thanks to the xmonad project: I took a look at their CI/CD -- and their representation of
the pipeline in the README -- as inspiration